🛠️ Waterfall Methodology · Lesson 4

🔨 Phase 3 & 4: Implementation and Testing

The Goal of Implementation

The Implementation phase involves the actual creation of the IT system based on the designs produced in the previous phase. Depending on the type of IT system being developed, this phase can involve a wide range of activities. The team translates the detailed design documents into working code, builds the necessary infrastructure, and prepares the system for real-world use.

Key Implementation Activities

Depending on the project, the implementation phase will involve some or all of the following:

💻 Coding & Infrastructure

Coding: Software engineers translate detailed design documents into working code, following predefined specifications and standards.
Building computer systems: Hardware engineers/technicians combine components, devices, and peripherals to form the infrastructure the system will run on.

🗄️ Data & Interfaces

Database creation: Software/database engineers build, populate, and link databases to provide back-end system processes.
Interface creation: Methods of interaction for users are created, including accessibility options and responsive layouts for different devices.

📝 Documentation: During this phase, the team also produces supporting documentation. This includes user guides to help end-users, as well as technical documentation with information and data to support future maintenance and improvement.

❓ Question 1 — Which of the following is a primary task during the Implementation phase?

A) Gathering requirements from stakeholders. B) Creating low-fidelity wireframes of the user interface. C) Translating design documents into working code and creating databases. D) Formally confirming the system is ready for deployment.

Why C is correct: The text states that Implementation involves "Coding: software engineers translate detailed design documents into working code" and "Database creation: software/database engineers will build, populate and link databases." Option A is Requirements Gathering, Option B is System Design, and Option D is Acceptance Testing (part of the Testing phase).

Entering the Testing Phase

Once the system is complete, the project moves to the Testing phase. During this phase, the development team carries out a series of activities to discover any issues that were not detected during implementation. The goal is not just to find bugs, but to ensure that all functional and non-functional requirements have been met, and that the system is robust, consistent, and reliable.

📋 The Log: During testing, all tests and their outcomes (including detailing any corrective actions taken) must be recorded. A detailed log is useful for auditing, quality assurance, and root cause analysis if a bug or issue arises in the future.

❓ Question 2 — What is the primary goal of the Testing phase?

A) To write new features for the system. B) To train end-users on how to use the system. C) To discover issues and ensure the system is robust, reliable, and meets requirements. D) To install the software on the client's servers.

Why C is correct: The text states that during testing, "the development team will carry out a series of activities to discover any issues... In addition to ensuring the system functions as expected, testing must ensure that all functional and non-functional requirements have been met and that the system is robust, consistent and reliable." Writing features is Implementation, training is Deployment, and installing software is also Deployment.

The Four Levels of Testing

There are four main types of testing used in the Waterfall methodology. They happen in a specific order, from the smallest piece of code to the full system:

1. Unit Testing

Performed by: Developers

Individual units or modules of code are tested to ensure they perform their specific functions correctly. Developers often use automated testing tools to rapidly test the unit/module against different scenarios and inputs.

2. Integration Testing

Performed by: Developers

When more than one unit is completed, the units are combined and tested together to verify that they work together. It considers questions like: Does the system continue to function as new units are added? Do units communicate correctly? Is data passed between units reliable?

3. System Testing

Performed by: QA Team

The entire system is tested against the predefined requirements and user needs. This typically involves manual testing by a dedicated QA team to simulate real-world usage scenarios.

4. Acceptance Testing

Performed by: Stakeholders / End Users

This final stage involves formal confirmation by stakeholders or end-users that the system meets their expectations and is ready for deployment.

❓ Question 3 — A QA team manually tests the entire system to simulate real-world user scenarios and ensure it matches the original business requirements. Which type of testing is this?

A) Unit Testing B) Integration Testing C) System Testing D) Acceptance Testing

Why C is correct: The text explicitly states: "System testing: the entire system is tested against the predefined requirements and user needs. This typically involves manual testing by a dedicated QA team to simulate real-world usage scenarios." Unit testing is for individual code modules, Integration testing combines modules, and Acceptance testing is the formal confirmation by stakeholders.

🎉 You've mastered the Implementation and Testing Phases!

Recap:
• Implementation: Coding, infrastructure setup, database creation, interface design, and documentation.
• Testing Goals: Discover bugs, ensure robustness, reliability, and meet all functional requirements.
• Testing Levels: Unit -> Integration -> System -> Acceptance. Each level has a specific focus and tester.

Ready to move on to the final phases: Deployment and Maintenance?